-
Notifications
You must be signed in to change notification settings - Fork 148
feat: Show sections/subsections/units available for sync in library sync page [FC-0097] #2271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Show sections/subsections/units available for sync in library sync page [FC-0097] #2271
Conversation
Thanks for the pull request, @ChrisChV! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. Where can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2271 +/- ##
==========================================
+ Coverage 94.41% 94.47% +0.06%
==========================================
Files 1167 1169 +2
Lines 24928 25136 +208
Branches 5416 5494 +78
==========================================
+ Hits 23535 23748 +213
+ Misses 1326 1317 -9
- Partials 67 71 +4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
On this step, I got this error after updating the Section. Could you verify if you get the same?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ChrisChV Nice work! 👍
- I tested this: (Tested links with different components and containers in courses)
- I read through the code
- I checked for accessibility issues
- Includes documentation
@ChrisChV This is due to incorrect (legacy url) EVENT_BUS_REDIS_CONNECTION_URL in edx-platform but should not have any effect here. |
@navinkarkera Thanks! One more question, in this case (publish the Unit), can you update the section in the course successfully? In my case, it is not like that; suddenly, it is the configuration of my instance
|
@ChrisChV Hmm, I had some weird issues yesterday while updating sections which I could not reproduce but today I was able to do it. Even after updating a section, it doesn't go away from the links page. I see below response from the API [
{
"id": 249,
"upstream_context_title": "CS3",
"upstream_version": 5,
"ready_to_sync": false,
"upstream_context_key": "lib:UNIX:UXLIB1",
"downstream_usage_key": "block-v1:UNIX+UX3+2025_T3+type@chapter+block@ab1c996f938f4de4b5f255f4d0672737",
"downstream_context_key": "course-v1:UNIX+UX3+2025_T3",
"top_level_parent_usage_key": null,
"version_synced": 5,
"version_declined": null,
"created": "2025-07-29T12:28:57.823885Z",
"updated": "2025-07-29T12:42:28.704113Z",
"upstream_key": "lct:UNIX:UXLIB1:section:1-section-from-lib-154bc8",
"upstream_type": "container"
}
]
|
@navinkarkera Thanks! I found the issue. I fixed it in openedx/edx-platform@34cd5a4 and openedx/edx-platform@2964783 |
@navinkarkera Yes, I have a Product question about this: #2168 (comment) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good to me.
Description
mockGetEntityLinks
tomockGetComponentEntityLinks
Supporting information
DownstreamListView
to get all components and container links [FC-0097] edx-platform#37024Testing instructions
make migrate
on cms shell.Check summary of libraries
2 component applied
.TODO: It's missing some changes in the counts of the summary (see #2168 (comment))
Check out of sync list with top-level parent logic
Note: This is the most basic way to test top-level parent logic; there are many more possibilities. I invite you to try several paths and possibilities.
Other information
TODO:
Best Practices Checklist
We're trying to move away from some deprecated patterns in this codebase. Please
check if your PR meets these recommendations before asking for a review:
.ts
,.tsx
).propTypes
,defaultProps
, andinjectIntl
patterns are not used in any new or modified code.src/testUtils.tsx
(specificallyinitializeMocks
)apiHooks.ts
in this repo for examples.messages.ts
files have adescription
for translators to use.../
. To import from parent folders, use@src
, e.g.import { initializeMocks } from '@src/testUtils';
instead offrom '../../../../testUtils'